ci: Fix celery #4765
Merged
ci: Fix celery #4765
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #4765 +/- ##
==========================================
- Coverage 84.78% 84.76% -0.02%
==========================================
Files 158 158
Lines 16323 16323
Branches 2792 2792
==========================================
- Hits 13839 13837 -2
- Misses 1668 1672 +4
+ Partials 816 814 -2 |
alexander-alderman-webb
approved these changes
Sep 5, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We have some newrelic interference/compatibility tests that were failing with the newest newrelic release. Looking at that release, newrelic completely rehauled their celery instrumentation, so I'm pinning our tests to only test against older newrelic versions where we had the problem in the first place.
Rerunning toxgen on the updated config also pulled in a new openai release.